Skip to content

Conversation

dgandhi62
Copy link
Contributor

@dgandhi62 dgandhi62 commented Oct 6, 2025

  • refactor: start notifications category migration

  • refactor: migrate pinpoint-helper to sdk v3

  • refactor: migrate channel handlers to sdk v3

  • refactor: migrate auth-helper to sdk v3

  • refactor: update test mocks for sdk v3

  • refactor: migrate cli logout command to sdk v3

  • refactor: migrate e2e-core pinpoint utils to sdk v3

  • fix: update package dependencies

  • fix: correct client import names

  • fix: yarn lock updates

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dgandhi62 dgandhi62 requested a review from a team as a code owner October 6, 2025 14:45
Copy link
Contributor

@ShadowCat567 ShadowCat567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some suggestions for improvements and questions

@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch 2 times, most recently from 9e2c76c to 712d1a3 Compare October 8, 2025 02:28
@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch from 712d1a3 to 58e77c8 Compare October 8, 2025 16:37
…n stacks are stuck

- Add failure predicate to treat _IN_PROGRESS states as failed after timeout
- Reduce timeout to 15 minutes to fail faster on stuck operations
- Prevents Jest worker processes from being killed due to hanging deletions
- Add sendEof() to In-App Messaging case to prevent hanging processes
- Add notifications-analytics-compatibility-in-app-2.test.ts to RUN_SOLO
  to prevent Jest worker memory issues
@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch from 6e7eed1 to ae486c9 Compare October 9, 2025 21:22
@dgandhi62 dgandhi62 closed this Oct 13, 2025
@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch from ff7e800 to 53e973b Compare October 13, 2025 02:23
@dgandhi62 dgandhi62 reopened this Oct 13, 2025
@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch from 1ece5b1 to c9528db Compare October 13, 2025 03:58
@dgandhi62 dgandhi62 force-pushed the category-notifications/sdk-v3-migration branch from 464ad5f to 7499c10 Compare October 13, 2025 14:32
Copy link
Contributor

@ShadowCat567 ShadowCat567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good, my comments are mostly questions.
You should merge dev into this branch to get rid of the merge conflicts.

ShadowCat567
ShadowCat567 previously approved these changes Oct 17, 2025
Copy link
Contributor

@ShadowCat567 ShadowCat567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, nice job!
Remember to run PR testing on this

@dgandhi62 dgandhi62 merged commit 2d0c169 into aws-amplify:dev Oct 21, 2025
5 checks passed
ShadowCat567 pushed a commit that referenced this pull request Oct 21, 2025
ShadowCat567 added a commit that referenced this pull request Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants